Repository navigation
Show country in CLI stats and events - #1
Merged
Merged
Conversation
dannyshmueli
marked this pull request as ready for review
October 9, 2026 05:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
statscurrently omits country groups, andeventshides the top-level country already returned by the API. Print a Countries section with each group's raw events and unique users, and display country beside each event. Missing country displays as Unknown; stats notes that users may appear in multiple countries.Requires Hosted's new
/statscountry field for the stats section. Older responses without it keep the existing output. The events change uses the existing API contract.Validation: 178 tests pass, including command-level rendering against mock HTTP responses with known/unknown countries and unchanged event properties.
Release after the Hosted API update. Merge this change, bump the CLI version, and publish through the repository's manual npm/OTP release procedure; pushing or merging this PR alone does not publish a new CLI package.